Repository navigation
docs(mcp): describe current heuristic summary sources - #2439
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current meeting-save pipeline writes heuristic
auto_summary_*frontmatter, which MCP parses alongside older local-summary fields/blocks and legacy sidecars. Its owner guide and loader comment instead described summaries as legacy-only. Correct those two descriptions without changing summary generation, model use, parsing, or search behavior. Meetings without indexable summary fields still contribute no summary rows.Addresses TOOLS-MCP-5. This extracts the two relevant factual documentation/comment corrections also pending in #2336; that broader PR is untouched. The separate action-item status correction is #2436.
Validation on
63da0ac26: all nine safe mapped checks passed, including 272 MCP fixture tests, source pins, module boundaries, file sizes, lint, and doc paths. The canonicalbash check.shresult remains FAIL becauserun-e2e-smoke.shwas explicitly blocked with exit 3: the main-based E2E fixture has a known real-profile defaults write and must run through the reviewed isolation union. The orchestration-only preflight entry is skipped by the runner; a separate actual preflight passed. The saved proof preserves the raw failure.verify-change.shselected no app check and markedTranscriptLoader.swiftfor hand verification. Its only changed lines are documentation comments; a comparison confirms all non-comment lines are unchanged. Independent coordinator review of the complete two-hunk diff against fetched origin/main: GREEN, no findings. Source trace covers the restyle subscription, heuristic writer, shared parser, loader fallback, and index insertion. No real capture library, model, SDK, host-client connection, or native app actions. Native E2E and host-client proof remain unverified.